fix(syncer/v2): use default ticker in integration tests#19398
Merged
fix(syncer/v2): use default ticker in integration tests#19398
Conversation
Contributor
|
👋 MStreet3, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
Unheilbar
approved these changes
Sep 17, 2025
|
DylanTinianov
approved these changes
Sep 17, 2025
This was referenced Sep 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
tickChexists to let tests override the default timing mechanism of the syncer. However, only one time value is sent down this channel yet the syncer v2 now has two goroutines that would read from this ticker (V1 only had one).This causes flaky tests because one or the other routine would get the signal leaving the other routine in starvation. The fix here is to just remove the default ticker override.
Requires
Supports